home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group01b.txt
/
000177_icon-group-sender_Sat Nov 24 15:41:08 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2002-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id fAOMdiI22387
for icon-group-addresses; Sat, 24 Nov 2001 15:39:44 -0700 (MST)
Message-Id: <200111242239.fAOMdiI22387@baskerville.CS.Arizona.EDU>
Date: Thu, 22 Nov 2001 15:38:27 -0700
X-Authentication-Warning: unicon.cs.nmsu.edu: jeffery set sender to jeffery@cs.nmsu.edu using -f
From: Clint Jeffery <jeffery@cs.nmsu.edu>
To: captnjameskirk@yahoo.com
CC: icon-group@cs.arizona.edu
Subject: Re: translation+link question; hello executable size
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 748
Windows Icon compiles and links VM code. The default .EXE extension
copies the VM into the .EXE along with the VM code, so your suspicion
is correct. If an extension of .CMD is specified (and maybe .BAT also,
I forget) the VM is not included, and must be present on the path in
order for the program to run.
A configuration which produces small .exe's and uses a VM in a .dll was
developed awhile back by David Feustel, and I hope to incorporate this under
control of a command line option in future releases. There are other size
issues in the Icon implementation, but (without speaking for the Icon
Project) my belief is that size is not a paramount concern in the design,
as it perhaps is for Java, for example.
Clint jeffery@cs.nmsu.edu